An inbound ACKNOWLEDGEMENT EDI message is an application error and acknowledgment message that an EDI trading partner sends to:
Acknowledge that they received an EDI message you sent.
Inform you that their application accepted or rejected the EDI message during processing.
The EDI trading partner must include a message function code in the BGM segment of the ACKNOWLEDGEMENT EDI message to indicate whether they accepted or rejected the EDI message. The Navis standard mapping file maps the following message function codes:
AP: The trading partner accepted the EDI message
Any other code or blank: The trading partner rejected the EDI message
The EDI trading partner should also include the following primary key, and any optional information, in the RFF segment of the ACKNOWLEDGEMENT EDI message based on the class of the inbound EDI message they processed:
|
EDI Message Class |
Primary Key |
Optional Information |
|---|---|---|
|
STOWPLAN |
Container number |
Vessel name and container's line operator |
|
ACTIVITY |
Container number |
Container's line operator and activity type |
|
PERFORMANCE |
Vessel name |
|
N4 uses this information to determine the associated outbound EDI transactions.
Depending on the message function codes and the information your EDI trading partner sends, you may need to edit the mapping file so that N4 will map them correctly.
The Navis supported ACKNOWLEDGEMENT EDI message is the APERAK EDI message.
After processing an ACKNOWLEDGEMENT EDI message, N4 displays the processed EDI data in the Transactions view and on Transactions tab for the associated EDI transactions. For example, if you receive APERAK messages in response to outbound ACTIVITY EDI messages, then N4 displays the processed APERAK data in the Transactions view and on Transactions tab for the associated outbound ACTIVITY EDI transactions. For more information, see Transactions view (on page 1).
To determine if you need to send an outbound EDI message in response to a rejected ACKNOWLEDGEMENT EDI message, you must monitor the Transactions view or on Transactions tab. For example, if you receive a rejected APERAK EDI message, you must correct the error and then manually send the associated outbound EDI message to the EDI trading partner. To resend an outbound ACTIVITY EDI message, see EDI Session form (on page 1). To resend an outbound EDI message for a vessel visit, such as a STOWPLAN EDI message, see Outbound EDI tab.
For more information on the APERAK EDI message, go to http://www.unece.org/trade/untdid/d00a/trmd/aperak_c.htm.